Facilitating method for handover of a mobile communication device

ABSTRACT

A target node includes an S1 interface which includes an interface between the target node and a gateway, an X2 interface which includes an interface between a source node and the target node, and a transceiver which receives data from the S1 interface and data from the X2 interface. The transceiver sends the data from the X2 interface before sending the data from the S1 interface to a mobile device after the mobile device completes a handover from the source node to the target node.

The present application is a Continuation Application of U.S. patentapplication Ser. No. 14/530,005 filed Oct. 31, 2014, which is aContinuation Application of U.S. patent application Ser. No. 13/412,666,filed on Mar. 6, 2012, now U.S. Pat. No. 8,891,484, which was aContinuation Application of U.S. patent application Ser. No. 12/310,157,filed on Feb. 13, 2009, now U.S. Pat. No. 8,228,869 B2, which was basedon International Application No. PCT/JP2007/066510, filed on Aug. 21,2007, which was based on and claims priority from UK patent applicationNo. 0616682.1, filed on Aug. 22, 2006 and UK patent application No.0619524.2, filed on Oct. 3, 2006, the disclosures of which areincorporated herein in their entirety by reference.

TECHNICAL FIELD

The present invention relates to mobile telecommunications networks,particularly but not exclusively networks operating according to the3GPP standards or equivalents or derivatives thereof. The presentinvention relates also to the management of data packets in the mobiletelecommunications networks.

BACKGROUND ART

In mobile telecommunications networks, there is a requirement for UserEquipment (UE) to handover from one base station to another. In the3GPP, there has been recently proposed a procedure defined in thecontrol plane (C-plane) for handover (HO) from a source eNodeB to atarget eNodeB. The various acronyms applicable to 3G communications willof course be familiar to those skilled in the art but a glossary isappended for the benefit of lay readers.

DISCLOSURE OF INVENTION

Although for efficiency of understanding for those of skill in the artthe invention will be described in detail the context of a 3G system,the principles of handover can be applied to other systems, e. g. otherCDMA or wireless in which a mobile device or User Equipment (UE)communicates with one of several other devices (corresponding to eNodeB)with the corresponding elements of the system changed as required.

It has been noted that with current 3GPP handover proposals [for exampleas set out in Handover of downlink user plane data for RT services,www.3gpp.org-/ftp/tsg ran/WG3 lu/TSGR3 51 bis/docs/R3-060454. zip], onlya few downlink (DL) data packets must be forwarded from source to targeteNodeB for real time services during handover execution. This mayresult, in the worst case, in a loss of single data packet or delayeddelivery. It has been generally considered that either of these eventscould be acceptable, it would naturally be desirable not to have dataloss but it has been considered to be inevitable given the operatingconstraints. It has been generally agreed that the user data should beforwarded from source eNodeB to target eNodeB for both real-time andnon-real-time services during the handover execution phase, rather thanby applying different mechanisms in a service dependent way.

According to the present invention, it has been proposed that data losscan in fact be avoided during handover, without necessarily complicatingsignalling or adding significant further overhead or delay. Theinvention stems from the appreciation that data loss can be avoided (orat least reduced) by implicit signalling without requiring explicitcontrol signals.

The applicant has recently proposed a lossless HO procedure. Thisproposal is set out inhttp://www.3gpp.org/ftp/tsg_ran/WG3_lu/TSGR3_53/docs/R3-061088.zip. Inthe proposed system, the source eNodeB stops transmitting data beforesending the HO command but continues receiving the data and the UE stopstransmitting data after it receives the HO command. After sending the HOcommand, DL data received at the source eNodeB from the Access Gatewayfor transmission to the UE is buffered and sent to the target eNodeB foronward delivery once the UE has established a communication link withthe target eNodeB. The present application describes a way in which thebuffering of the data can be managed in the source eNodeB. Forcompleteness, a description will also be given of the original proposalfor lossless handover.

According to a first aspect of the present invention, there is provideda method of facilitating handover of a mobile communication device froma source node to a target node, the method comprising buffering receiveduser data packets in the target node during handover prior to sending tothe mobile device.

According to a second aspect of the present invention, there is provideda target node of a mobile communication system comprising:

means for receiving a handover request, requesting handover of a mobiledevice from a source node to the target node;

means for sending a handover response;

means for receiving user data packets during handover, for transmissionto the mobile device;

means for sending user data packets to the mobile device after handovercompletion; and

means for buffering the received user data packets during handover priorto sending to the mobile device.

According to a third aspect of the present invention, there is provideda target node of a mobile communication system comprising:

a first receiver operable to receive a handover request, requestinghandover of a mobile device from a source node to the target node;

a first transmitter operable to transmit a handover response;

a second receiver operable to receive user data packets during handover,for transmission to the mobile device;

a second transmitter operable to transmit user data packets to themobile device after handover completion; and

a buffer operable to buffer the received user data packets duringhandover prior to transmission to the mobile device.

According to a fourth aspect of the present invention, there is provideda method of facilitating handover of a mobile communication device froma source node to a target node, the method comprising, in response toreceipt of a handover response at the source node, stopping forwardingof downlink user data packets to the mobile communication device whilstcontinuing to receive uplink user data packets from the user device andsending a handover command to the mobile device.

According to a fifth aspect of the present invention, there is provideda source node of a mobile communication system comprising:

means for forwarding downlink data packets to a mobile communicationdevice;

means for receiving uplink user data packets from the mobilecommunication device;

means for receiving a handover response indicating handover of themobile communication device from the source node to a target node;

means for controlling said forwarding means, in response to receipt ofsaid handover response, so that said forwarding means stops forwardingsaid downlink user data packets to the mobile communication devicewhilst said receiving means continues to receive uplink user datapackets from the user device; and

means for sending a handover command to the mobile device after saidforwarding means stops forwarding said downlink user data packets.

According to a sixth aspect of the present invention, there is provideda method of facilitating handover of a mobile communication device froma source node to a target node during which handover user data packetsare forwarded from the source node to the target node, the methodcomprising receiving forwarded data packets at the target node from thesource node via a first interface and receiving data packets from anexternal source via a second interface and ordering the data packets fortransmission to the mobile communication device based on the interfacefrom which the data packets are received.

According to a seventh aspect of the present invention, there isprovided a target node of a communication network comprising:

a first interface for receiving, during handover of a mobile device froma source node to the target node, downlink user data packets from thesource node;

a second interface for receiving user data packets for the mobile devicefrom an external source; and

means for ordering the data packets for transmission to the mobilecommunication device based on the interface from which the data packetsare received.

According to an eighth aspect of the present invention, there isprovided a communication method performed in a source node of atelecommunication system, the method comprising:

receiving Service Data Units, SDUs, for transmission to a mobilecommunication device;

storing a copy of the SDUs in an SDU management buffer;

passing the SDUs to a concatenation and segmentation unit to generateProtocol Data Units, PDUs;

storing the PDUs in a transmit buffer for transmission to the mobilecommunication device;

sending a feedback message to the SDU management buffer identifying anSDU that can be removed from the SDU management buffer when, forUnacknowledge Mode, UM, data, the PDUs corresponding to that SDU havebeen forwarded from the transmission buffer or when, for AcknowledgeMode, AM, data, receipt of the PDUs corresponding to that SDU have beenacknowledged by the mobile communication device;

in response to the receipt of the feedback message, removing theidentified SDU from the SDU management buffer; and

during handover of the mobile communication device from the source nodeto a target node, forwarding SDUs for the mobile communication device tothe target node in dependence upon the SDUs stored in said SDUmanagement buffer.

According to a ninth aspect of the present invention, there is provideda source node of a telecommunication system, the source node comprising:

means for receiving Service Data Units, SDUs, for transmission to amobile communication device;

an SDU management buffer for storing a copy of the SDUs;

a concatenation and segmentation unit for generating Protocol DataUnits, PDUs from the SDUs;

a transmission buffer for storing the PDUs prior to transmission to themobile communication device;

means for sending a feedback message to the SDU management bufferidentifying an SDU that can be removed from the SDU management bufferwhen, for Unacknowledge Mode, UM, data, the PDUs corresponding to thatSDU have been forwarded from the transmission buffer or when, forAcknowledge Mode, AM, data, receipt of the PDUs corresponding to thatSDU have been acknowledged by the mobile communication device;

means for removing, in response to the receipt of the feedback message,the identified SDU from the SDU management buffer; and

means for forwarding, during handover of the mobile communication devicefrom the source node to a target node, SDUs for the mobile communicationdevice to the target node in dependence upon the SDUs stored in said SDUmanagement buffer.

According to a tenth aspect of the present invention, there is provideda communication method performed in a mobile communication device of atelecommunication system, the method comprising:

receiving Service Data Units, SDUs, for transmission to a source node ofthe telecommunication system;

storing a copy of the SDUs in an SDU management buffer;

passing the SDUs to a concatenation and segmentation unit to generateProtocol Data Units, PDUs;

storing the PDUs in a transmit buffer for transmission to the sourcenode;

sending a feedback message to the SDU management buffer identifying anSDU that can be removed from the SDU management buffer when, forUnacknowledge Mode, UM, data, the PDUs corresponding to that SDU havebeen forwarded from the transmission buffer or when, for AcknowledgeMode, AM, data, receipt of the PDUs corresponding to that SDU have beenacknowledged by the source node;

in response to the receipt of the feedback message, removing theidentified SDU from the SDU management buffer;

receiving a status report from the source node;

receiving a handover command from the source node after receiving thestatus report; and

after completing handover to a target node, using the received statusreport to control which SDUs are passed to the concatenation andsegmentation unit to form PDUs for transmission to the target node.

According to an eleventh aspect of the present invention, there isprovided a mobile communication device comprising:

means for receiving Service Data Units, SDUs, for transmission to asource node of the telecommunication system;

an SDU management buffer for storing a copy of the SDUs;

a concatenation and segmentation unit for generating Protocol DataUnits, PDUs from the SDUs;

a transmit buffer for storing the PDUs prior to transmission to thesource node;

means for sending a feedback message to the SDU management bufferidentifying an SDU that can be removed from the SDU management bufferwhen, for Unacknowledge Mode, UM, data, the PDUs corresponding to thatSDU have been forwarded from the transmission buffer or when, forAcknowledge Mode, AM, data, receipt of the PDUs corresponding to thatSDU have been acknowledged by the source node;

means for removing, in response to the receipt of the feedback message,the identified SDU from the SDU management buffer;

means for receiving a status report from the source node;

means for receiving a handover command from the source node afterreceiving the status report; and

means for using, after completing handover to a target node, thereceived status report to control which SDUs are passed to theconcatenation and segmentation unit to form PDUs for transmission to thetarget node.

According to a twelfth aspect of the present invention, there isprovided a method performed by a source node of a telecommunicationnode, the method comprising:

buffering downlink user data packets for transmission to a mobilecommunication device in a buffer;

sending downlink user data packets to the mobile communication device;

receiving a handover response indicating handover of the mobilecommunication device to a target node; and

selectively forwarding user data packets from said buffer to said targetnode in dependence upon an RLC status report or HARQ feedbackinformation.

According to a thirteenth aspect of the present invention, there isprovided a communication method performed in a source node of atelecommunication system, the method comprising:

receiving Service Data Units, SDUs, for transmission to a mobilecommunication device;

storing a copy of the SDUs in an SDU management buffer;

passing the SDUs to a concatenation and segmentation unit to generateProtocol Data Units, PDUs;

storing the PDUs in a transmit buffer for transmission to the mobilecommunication device;

sending a feedback message to the SDU management buffer identifying anSDU that can be removed from the SDU management buffer when, forUnacknowledge Mode, UM, data, the PDUs corresponding to that SDU havebeen forwarded from the transmission buffer or when, for AcknowledgeMode, AM, data, receipt of the PDUs corresponding to that SDU have beenacknowledged by the mobile communication device;

in response to the receipt of the feedback message, removing theidentified SDU from the SDU management buffer; and

during handover of the mobile communication device from the source nodeto a target node, selectively forwarding SDUs for the mobilecommunication device to the target node in dependence upon an RLC statusreport or HARQ feedback information.

According to a fourteenth aspect of the present invention, there isprovided a source node of a telecommunication node, the source nodecomprising:

a buffer for buffering downlink user data packets for transmission to amobile communication device;

means for sending downlink user data packets to the mobile communicationdevice;

means for receiving a handover response indicating handover of themobile communication device to a target node; and

means for selectively forwarding user data packets from said buffer tosaid target node in dependence upon an RLC status report or HARQfeedback information.

According to a fifteenth aspect of the present invention, there isprovided a source node of a telecommunication system, the source nodecomprising:

means for receiving Service Data Units, SDUs, for transmission to amobile communication device;

an SDU management buffer for storing a copy of the SDUs;

a concatenation and segmentation unit for generating Protocol DataUnits, PDUs;

a transmit buffer for storing the PDUs for transmission to the mobilecommunication device;

means for sending a feedback message to the SDU management bufferidentifying an SDU that can be removed from the SDU management bufferwhen, for Unacknowledge Mode, UM, data, the PDUs corresponding to thatSDU have been forwarded from the transmission buffer or when, forAcknowledge Mode, AM, data, receipt of the PDUs corresponding to thatSDU have been acknowledged by the mobile communication device;

means for removing, in response to the receipt of the feedback message,the identified SDU from the SDU management buffer; and

means for selectively forwarding, during handover of the mobilecommunication device from the source node to a target node, SDUs for themobile communication device to the target node in dependence upon an RLCstatus report or HARQ feedback information.

According to a sixteenth aspect of the present invention, there isprovided a method of facilitating handover of a mobile communicationdevice from a source node to a target node, the method comprising:

at the source node, in response to receiving a handover response fromthe target node: sending a status packet to the mobile communicationdevice and after sending the status packet stopping the transmission ofdownlink user data from the source node to the mobile communicationdevice; and

at the mobile communication device, in response to receiving a handovercommand from the source node: sending a status packet to the source nodeand after sending the status packet stopping the transmission of uplinkuser data from the mobile communication device to the source node.

According to a seventeenth aspect of the present invention, there isprovided a source node of a telecommunication system, the source nodecomprising:

means for receiving uplink user data packets from a mobile communicationdevice;

means for transmitting downlink user data packets to the mobilecommunication device;

means for receiving a handover response indicating handover of themobile communication device from the source node to a target node;

means for generating, in response to receipt of said handover response,a status report indicating uplink data packets received from the mobilecommunication device;

means for sending the generated status report to the mobilecommunication device; and

means for stopping the transmission of downlink user data from thesource node to the mobile communication device after sending said statusreport.

According to an eighteenth aspect of the present invention, there isprovided a mobile communication device comprising:

means for receiving downlink user data packets from a source node of atelecommunication system;

means for transmitting uplink user data packets to said source node;

means for receiving a handover command from the source node indicatinghandover to a target node of the telecommunication system;

means for generating, in response to receiving said handover command, astatus packet indicating downlink user data packets that have beenreceived;

means for sending the status report to the source node; and

means for stopping the transmission of uplink user data packets from themobile communication device to the source node after sending said statusreport.

According to a nineteenth aspect of the present invention, there isprovided a method of facilitating handover of a mobile communicationdevice from a source node to a target node, the method being performedin the source node and comprising:

receiving a status packet from the mobile communication device; and

forwarding user data packets to the target node in dependence uponinformation contained in the received status packet.

According to a twentieth aspect of the present invention, there isprovided a source node of a telecommunication system, the source nodecomprising:

means for receiving a handover response from a target node indicatinghandover of a mobile communication device from the source node to thetarget node;

means for stopping, in response to receiving said handover response,transmission of downlink user data from the source node to the mobilecommunication device;

means for transmitting a handover command to said mobile communicationdevice after stopping the transmission of said downlink user data;

means for receiving a status packet from the mobile communicationdevice; and

means for forwarding user data packets to the target node in dependenceupon information contained in the received status packet.

According to a twenty-first aspect, user data transmission is stoppedimplicitly, without requiring further signalling overhead, when a node“realizes” that a handover is in progress This solution departs from theconventional philosophy of signalling actions to be performed andrequires a modification to a conventional node to relate control plane(C-plane) and user plane (U-plane) activity but has benefits asdiscussed.

Preferably data packets are forwarded from a source to a target nodeduring handover, this avoids the need for retransmission from theexternal source to the target node.

Preferably the packets are ordered at the target node prior to sending.It has been appreciated that the ordering can be made more efficient andelegant by a further related use of implicit signalling, based on theinterface by which the target node receives the packets. This may beindependently provided in a twenty-second aspect.

Preferably the downlink packets are buffered at the target node. Thismay seem contrary to the conventional principle of forwarding packetswith minimal delay but it has been appreciated that the delay is smalland the net effect, even for time critical services such as Voice overIP may be beneficial. This feature may be independently provided in atwenty-third aspect.

Preferably, in addition to suspending downlink activity, uplink activityis also implicitly suspended, and this is provided independently in atwenty-fourth aspect.

Preferably the uplink packets are buffered in the mobile device. As withthe twenty-third aspect, this may seem contrary to the conventionalprinciple of forwarding packets with minimal delay but it has beenappreciated that the delay is small and the net effect, even for timecritical services such as Voice over IP may be beneficial. This featuremay be independently provided in a twenty-fifth aspect.

A particularly advantageous feature of the above aspects is that theyfacilitate separate suspending of uplink and downlink data transmission.Thus, contrary to conventional proposals, a source node may suspendtransmission but continue reception of user data and thus packets mtransit are not lost. This may be provided independently in atwenty-sixth aspect.

Whilst each of the features may be provided independently to provideadvantages, for example downlink packets may be suspended withoutsuspending uplink packets or by using a different mechanism to suspenduplink packets or vice versa (and this may be advantageous where it iseasier to modify only one of the user equipment or the base), there is aparticular advantage to providing implicit suspension of both uplink anddownlink data. Similarly while buffering data packets during handovermay in itself improve use of the air interface and implicit ordering ofpackets may simplify processing, the complete suite of closelyinter-related but independent features mentioned above, includingbuffering and implicit ordering at the target node gives a highlyefficient mechanism for avoiding data loss with negligible overhead.

According to a twenty-seventh aspect, the present invention provides acommunication method performed in a telecommunication system, the methodcomprising: receiving Service Data Units, SDUs, for transmission to amobile communication device; storing a copy of the SDUs in an SDUmanagement buffer; passing the SDUs to a concatenation and segmentationunit to generate Protocol Data Units, PDUs; storing the PDUs in atransmit buffer for transmission to the mobile communication device;sending a feedback message to the SDU management buffer identifying anSDU that can be removed from the SDU management buffer when, forUnacknowledge Mode, UM, data, the PDUs corresponding to that SDU havebeen forwarded from the transmission buffer or when, for AcknowledgeMode, AM, data, receipt of the PDUs corresponding to that SDU have beenacknowledged by the mobile communication device; and in response to thereceipt of the feedback message, removing the identified SDU from theSDU management buffer.

The method may be performed in the node of a telecommunications networkor in a user equipment, such as a mobile telephone. When performed in anode and the node receives a handover response from a target node, thesource node stops forwarding user data packets to the mobilecommunication device and forwards SDUs stored in the SDU managementbuffer to the target node.

Preferably the source node continues to receive user data packets fromthe mobile communication device after stopping forwarding user datapackets to the mobile communications device. If those received datapackets include acknowledgements for any AM PDUs and, if appropriate,another feedback message is sent to the SDU management buffer to removean SDU from the SDU management buffer before it is forwarded to thetarget node.

Forwarded SDUs received at the target node from the source node are sentto the mobile communication device after completion of handover from thesource node to the target node.

In the case of AM mode data, the feedback message is sent to the SDUmanagement buffer from a PDU retransmission buffer and management entityafter the PDU retransmission buffer and management entity has receivedacknowledgement receipts for all the PDUs corresponding to the SDU.

In the case of UM mode data, the feedback message is sent to the SDUmanagement buffer by the transmit buffer after all the PDUscorresponding to the SDU have been forwarded from the transmissionbuffer.

According to a twenty-eighth aspect, the invention provides a method offacilitating handover of a mobile communication device from a sourcenode to a target node, the method comprising:

at the source node, in response to receiving a handover response fromthe target node, sending a status packet to the mobile communicationdevice and after sending the status packet stopping the transmission ofdownlink user data from the source node to the mobile communicationdevice, and

at the mobile communication device, in response to receiving a handovercommand from the source node, sending a status packet to the source nodeand after sending the status packet stopping the transmission of uplinkuser data from the mobile communication device to the source node.

This method may be implemented in addition to or separately from themethod of the twenty-seventh aspect mentioned above.

In one embodiment the information contained in the status packetreceived by the source node from the mobile communication device is usedto select user data packets held by the source node to be forwarded fromthe source node to the target node.

According to a twenty-ninth aspect, the invention provides a method offacilitating handover of a mobile communication device from a sourcenode to a target node, the method being performed in the source node andcomprising, in response to receiving a handover response from the targetnode:

stopping the transmission of downlink user data from the source node tothe mobile communication device;

transmitting a handover command to said mobile communication deviceafter stopping the transmission of said downlink user data;

receiving a status packet from the mobile communication device, and

forwarding user data packets to the target node in dependence uponinformation contained in the received status packet.

This method may also be implemented in addition to or separately fromthe methods of the twenty-eighth and the twenty-seventh aspectsdescribed above.

While the invention is described for ease of understanding in thecontext of handover from one 3G eNodeB to another, the principles may beextended to handover between nodes of different networks, e. g. a 3Gnetwork and another network.

The invention provides, for all methods disclosed, correspondingcomputer programs or computer program products for execution oncorresponding equipment, the equipment itself (user equipment, nodes orcomponents thereof) and methods of updating the equipment.

BRIEF DESCRIPTION OF THE DRAWINGS

Exemplary embodiments of the invention will now be described, by way ofexample, with reference to the accompanying drawings in which:

FIG. 1 schematically illustrates a mobile telecommunication system of atype to which a first exemplary embodiment of this invention isapplicable;

FIG. 2 schematically illustrates a base station according to the firstexemplary embodiment;

FIG. 3 schematically illustrates a mobile communication device accordingto the first exemplary embodiment;

FIG. 4 shows a related handover process;

FIG. 5 shows a modified handover process according to the firstexemplary embodiment;

FIG. 6 schematically illustrates a mobile telecommunication system of atype to which a second exemplary embodiment of this invention isapplicable;

FIG. 7 schematically illustrates a base station forming part of thesystem shown in FIG. 6;

FIG. 8 schematically illustrates a mobile communication device formingpart of the system shown in FIG. 6;

FIG. 9 illustrates part of a protocol stack forming part of thecommunication software used to control communications between the mobilecommunication device and the base stations;

FIG. 10 shows a related handover process;

FIG. 11 shows a modified handover process;

FIG. 12 illustrates the operation of the outer ARQ entity for managingthe buffering of acknowledge mode data packets during the handoverprocess;

FIG. 13 illustrates the operation of the outer ARQ entity for managingthe buffering of unacknowledge mode data packets during the handoverprocess.

BEST MODE FOR CARRYING OUT THE INVENTION

Referring to FIGS. 1-5, a first exemplary embodiment of this inventionwill now be described.

FIG. 1 schematically illustrates a mobile (cellular) telecommunicationsystem 1 in which users of mobile telephones (MT) 3-0, 3-1, and 3-2 cancommunicate with other users (not shown) via a base station 5 and atelephone network 7. In this embodiment (that is, the first exemplaryembodiment of this invention), the base station 5 uses an orthogonalfrequency division multiple access (OFDMA) technique in which the datato be transmitted to the mobile telephones 3 is modulated onto aplurality of sub-carriers. Different sub-carriers are allocated to eachmobile telephone 3 depending on the supported bandwidth of the mobiletelephone 3 and the amount of data to be sent to the mobile telephone 3.In this embodiment, the base station 5 also allocates the sub-earnersused to carry the data to the respective mobile telephones 3 in order totry to maintain a uniform distribution of the mobile telephones 3operating across the base station's bandwidth.

Base Station

FIG. 2 is a block diagram illustrating the mam components of the basestation 5 used in this embodiment. As shown, the base station 5 includesa transceiver circuit 21 which is operable to transmit signals to and toreceive signals from the mobile telephones 3 via one or more antennae 23(using the above described sub-carriers) and which is operable totransmit signals to and to receive signals from the telephone network 7via a network interface 25. The operation of the transceiver circuit 21is controlled by a controller 27 in accordance with software stored inmemory 29. The software includes, among other things, an operatingsystem 31 and a downlink scheduler 33. The downlink scheduler 33 isoperable for scheduling user data packets to be transmitted by thetransceiver circuit 21 in its communications with the mobile telephones3. The software also includes a handover module 35, the operation ofwhich will be described below.

Mobile Telephone

FIG. 3 schematically illustrates the mam components of each of themobile telephones 3 shown in FIG. 1. As shown, the mobile telephones 3include a transceiver circuit 71 that is operable to transmit signals toand to receive signals from the base station 5 via one or more antennae73. As shown, the mobile telephone 3 also includes a controller 75 whichcontrols the operation of the mobile telephone 3 and which is connectedto the transceiver circuit 71 and to a loudspeaker 77, a microphone 79,a display 81, and a keypad 83. The controller 75 operates in accordancewith software instructions stored within memory 85. As shown, thesesoftware instructions include, among other things, an operating system87. In this embodiment, the memory also provides an uplink data buffer89. The software for controlling the handover process is provided by ahandover module 91, the operation of which will be described below.

In the above description, both the base station and mobile device aredescribed for ease of understanding as having respective discretehandover modules which implement certain of the inventive features.Whilst the features may be provided in this way for certainapplications, for example where an existing system has been modified toimplement the invention, in other applications, for example in systemsdesigned with the inventive features in mind from the outset, thehandover features may be built into the overall operating system or codeand so a handover module as a discrete entity may not be discernible.

Description of the Related Handover Protocol

Before describing the inventive features further in detail, it may behelpful to summarize related handover protocol, with reference to FIG.4. The related signalling flow for the control plane is taken as thebasis for further discussion. The description from TR 25.912 for thesignalling sequence is also included.

-   1) The UE context within the source eNodeB contains information    regarding roaming restrictions which where provided either at    connection establishment or at the last TA update.-   2) The source eNodeB entity configures the UE measurement procedures    according to the area restriction information. Measurements provided    by the source eNodeB entity may assist the function controlling the    UE's connection mobility.-   3) Based-on measurement-results from-the UE and the source eNodeB,    probably assisted by additional RRM specific information, the source    eNodeB decides to handover the UE to a cell controlled by the target    eNodeB.-   4) The source eNodeB issues a handover Request to the target eNodeB    entity passing necessary information to prepare the handover at the    target side. The target eNodeB configures the required resources.-   5) Admission Control is performed by the target eNodeB to increase    the likelihood of a successful handover, if the resources can be    granted by target eNodeB.-   6) The handover preparation is finished at the target side,    information for the UE to reconfigure the radio path towards the    target side is passed to the source eNodeB.-   A) from step 7) until 12) means to avoid data toss during handover    are provided.-   7) The UE is commanded by the source eNodeB entity to perform the    handover, target side radio resource information is contained.-   8) The UE gains synchronization at the target side.-   9) Once the UE has successfully accessed the cell, it sends an    indication to the target eNodeB that the handover is completed.-   10) The MME/UPE is informed that the UE has changed cell. The UPE    switch the data path to the target side and can release any    U-plane/TNL resources towards the source eNodeB.-   11) The MME/UPE confirms the handover Complete message with the    handover Complete ACK message.-   12) The target eNodeB triggers the release of resources at the    source side. The target eNodeB can send this message directly after    reception of message 9.-   13) Upon reception of the Release Resource message, the source    eNodeB can release radio and C-plane related resources in relation    to the UE context. The source eNodeB should continue to perform data    forwarding until an implementation dependent mechanism decides that    data forwarding can be stopped and U-plane/TNL resources can be    released.-   14) If the new cell is member of a new Tracking Area, the UE needs    to register with the MME/UPE which in turn updates the area    restriction information on the target side.

The description that follows mainly applies to acknowledge mode RLCalthough the outer ARQ entity for LTE may not be identical to the RLC inall aspects. Specifics of unacknowledged mode RLC entities employed forreal time applications such as VoIP and streaming are also brought outwherever there is a different handling applied as compared to theacknowledge mode entities.

In order to transfer the context and forward the data to supportlossless inter eNodeB handover, we have appreciated that it is desirablethat the source eNodeB is able to synchronize the data transmissionstatus between itself and target data eNodeB during handover. From thiswe have concluded that the data flow should desirably be stopped at anappropriate instant in time during handover execution phase consideringthat the interruption time for the user plane data is minimal. However,fulfilling this desired requirement is not straightforward as stoppingthe data transmission through additional signalling would be problematicas it would an increase the overall handover time. We have appreciatedthat it is possible implicitly to stop the data transmission in (one orboth, preferably both) the source eNodeB and UE at the time of handoverexecution, by modifying the conventional arrangement to build in some“realization” of the handover process in the User data transfer process.A further desirable feature is that, whether, RLC SDUs or RLC PDUs basedforwarding is adopted, the number of duplicated packets transmitted overthe air either by the target ENB or by the UE is minimized.

We have proposed that the signalling sequence in FIG. 4 be modified asshown in FIG. 5 which shows timings when we propose the datatransmission in DL and UL are stopped with the details of the modifiedsequences described. We explain below how this approach of stopping thedata flow facilitates achieving a fast lossless handover for LTE.

Referring to FIG. 5, information flow for Intra-LTE-Access MobilitySupport is described.

-   1) The UE context within the source eNodeB contains information    regarding roaming restrictions which were provided either at    connection establishment or at the last TA update.-   2) The source eNodeB entity configures the UE measurement procedures    according to the area restriction information. Measurements provided    by the source eNodeB entity may assist the function controlling the    UE's connection mobility.-   3) Based on measurement results from the UE and the source eNodeB,    probably assisted by additional RRM specific information, the source    eNodeB decides to handover the UE to a cell controlled by the target    eNodeB.-   4) The source eNodeB issues a handover Request to the target eNodeB    entity passing necessary information to prepare the handover at the    target side. The target eNodeB configures the required resources.-   5) Admission Control is performed by the target eNodeB to increase    the likelihood of a successful handover, if the resources can be    granted by target eNodeB.-   6) The handover preparation is finished at the target side,    information for the UE to reconfigure the radio path towards the    target side is passed to the source eNodeB.-   7) This step consists of the following sub steps.

a. Before submitting HO Command to the lower layers, the RRC entity ineNB commands the RLC UP entities to stop the DL transmission so that RLCentities shall not submit any RLC PDUs to lower layer. The UL receptioncould continue. In case receiving entities are UM RLC entities, it willreassemble SDUs and transfer them to the upper layers as soon as allPDUs that contain the SDU have been received. As regards the AM RLCentities, if a Piggybacked ACK/NACK feedback is found in an AMD PDU, itis delivered to the Retransmission buffer & Management Unit at thetransmitting side of the AM RLC entity, in order to purge the buffer ofpositively acknowledged AMD PDUs.

b. The UE is commanded by the source eNB entity to perform the HO,target side radio resource information is contained.

c. On receiving the HO Command the RRC entity in the UE would commandthe RLC UP entities to stop the UL transmission. The UE shallimmediately initiate the L1/L2 signalling in the target eNodeB afterthis.

d. Since the user plane data transmission is stopped in both directions,the source eNodeB will be able to accurately synchronize the datatransmission status between source and target eNB, DL SDU forwardingcould start from any point after this.

-   8) The UE gains synchronization at the target side.-   9) Once the UE has successfully accessed the cell, it sends an    indication to the target eNodeB that the handover is completed.-   10a) After submitting the handover Complete to lower layer, RRC    entity in UE shall command the RLC UP entities to resume the UL UP    traffic.-   10b) On reception of handover Complete the RRC entity in eNodeB    shall command the RLC entities to resume the DL traffic. eNodeB    shall start the transmission of the forwarded DL packets received    from the source eNodeB.-   11) The MME/UPE is informed that the UE has changed cell. The UPE    switch the data path to the target side and can release any    U-plane/TNL resources towards the source eNodeB.-   12) The MME/UPE confirms the handover Complete message with the    handover Complete ACK message.-   13) The target eNodeB triggers the release of resources at the    source side. The target eNodeB can send this message directly after    reception of message 9.-   14) Upon reception of the Release Resource message, the source    eNodeB can release radio and C-plane related resources in relation    to the UE context. The source eNodeB should continue to perform data    forwarding until an implementation dependent mechanism decides that    data forwarding can be stopped and U-plane/TNL resources can be    released.-   15) If the new cell is member of a new Tracking Area, the UE needs    to register with the MME/UPE which in turn updates the area    restriction information on the target side.

The precise timings that are indicated above for stopping the data flowhelp in meeting the following (separate) desiderata we have formulated.

I. Unified Lossless handover mechanism for both real-time and nonreal-time services.

II. Minimal interruption time for the user plane data.

III. Minimizing transmission of duplicate packets by eNodeB and UE.

Desideratum I is met by having the RLC entities which are capable ofbuffering and forwarding the DL data packets form source to targeteNodeB. In the UE the RLC entities may buffer the data packets generatedby the application after the UL transmission is stopped till, the UE isswitched to the target eNodeB—this requires the UE to provide bufferingnot present in a conventional UE, but this may not be unduly problematicto implement By implicitly stopping the data flows the source eNodeBcould synchronize the data transmission status between source and targeteNodeB. This is because the source eNodeB can know accurately which arethe DL SDU that need to be transferred to the target eNodeB based on thedata in the transmission and retransmission buffer of AM RB and inTransmission buffer of UM RB as this remains static after the data flowis stopped.

Regarding the desideratum II, since there is no explicit (additional)signaling involved for stopping the data flow in the UL as well as DLdirection, there will be no increase in the interruption time for theuser plane data.

Furthermore, the instance when the DL data is stopped is chosen to bemost optimal according to our considerations so as to have minimuminterruption time. If the eNodeB continues to schedule DL data, the UEwill not be able to successfully receive or acknowledge these datapackets as, immediately after receiving the handover command, it wouldtry to synchronies with the target cell. Eventually these packets wouldhave to be forwarded to the target eNodeB and will have to betransmitted again through the target eNodeB resulting in inefficientusage of the air interface bandwidth. Whilst according to conventionalthinking it might be argued that for real-time services such as VoIP,stopping the data would be detrimental to the service, we haveappreciated that if eNodeB continues to transmit DL packets there is nomechanism that they could be recovered if the UE could not receive themwhile it was trying to synchronies with the target cell and this mightin practice be at least as problematic. However we have appreciated thatif data flow is stopped and a packet forwarding mechanism is adopted,there is a possibility to eliminate packet loss in DL although therecould be a delayed data packet delivery to the UE which could result injust a single packet being discarded in the worst case. But these couldbe compensated through the play-out buffer.

Similarly if the UE continues to transmit in the UL while trying to gainsynchronization with the target cell, it may not be able to receiveacknowledgement from the source eNodeB and UE would have to againtransmit these AM RLC packets in the UL direction to the target eNodeBresulting in inefficient usage of the air interface bandwidth. For thereal time services, packets that are transmitted in the UL direction bythe UE while it is trying to gain synchronization in the target cell,may get lost due to the bad radio conditions in UL and could not berecovered if the data flow is not stopped. Hence it would be beneficialto avoid any packet loss even for real time services in the UL bystopping the UL data flow during handover execution while the delaycould be compensated at the receiving end by play out buffer.

Furthermore if the transmission of data continues both in the UL and DLdirection after the handover Command is sent by the eNodeB it would becomplicated to synchronize the data transmission status between sourceand target data eNodeB because of the dynamic nature of the packets inthe transmission and retransmission buffers at the source eNodeB andwould result in duplicated packets being transmitted again by the targeteNodeB in DL and UE in the UL to ensure lossless handover for NRTServices resulting in inefficient usage of the air interface bandwidth.Although there will be inefficient air interface bandwidth usage, thetarget eNB and UE could ensure lossless HO. However, for real-timeservices such as VoIP etc using UM mode, data packets transmitted bysource and not received correctly at the target, will be lost and cannotbe recovered. Hence stopping the data flow for both RT and NRT servicesin a unified way will help in better resource utilization on the airinterface for the NRT Bearers and avoiding the data loss for RTservices.

Another advantage of having a definitive time instance for stopping thedata flow is that a simplified implicit reordering in the target eNodeBcould be achieved if the forwarded DL data packets from the sourceeNodeB on the X2 interface are transmitted first to the UE followed bythe data received from the AGW on S1 interface.

From the above discussion it seems desirable to stop the UL and DL datatransmission during the handover execution for both RT and NRT Servicesto support lossless Inter eNodeB handover, while aiming to keep theinterruption time and transmission of duplicate packets to a minimum.

We have disclosed in detail a mechanism for supporting lossless intereNodeB handover while aiming to keep the interruption time andtransmission of duplicate packets to a minimum and simplifying thecontext transfer and reordering at the target eNodeB.

Glossary of 3GPP Terms

-   LIE—Long Term Evolution (of UTRAN)-   eNB—E-UTRANNodeB-   UE—User Equipment—mobile communication device-   DL—downlink—link from base to mobile-   UL—uplink—link from mobile to base-   MME—Mobility Management Entity-   UPE—User Plane Entity-   HO—Handover-   RLC—Radio Link Control-   RRC—Radio Resource Control-   SDU—Service Data Unit-   PDU—Protocol Data Unit-   TA—Tracking Area-   UP—User Plane-   TNL—Transport Network Layer-   S1 Interface—Interface between aGW and eNB-   X2 Interface—Interface between two eNB

Referring to FIGS. 6-13, a second exemplary embodiment of this inventionwill be described hereunder.

Overview

FIG. 6 schematically illustrates a mobile (cellular) telecommunicationsystem 1 in which users of mobile telephones (MT) 3-0, 3-1, and 3-2 cancommunicate with other users (not shown) via one of the base stations5-1 or 5-2 and a telephone network 7. In this embodiment (that is, thesecond exemplary embodiment of this invention), the base stations 5 usesan orthogonal frequency division multiple access (OFDMA) technique inwhich the data to be transmitted to the mobile telephones 3 is modulatedonto a plurality of sub-carriers. Different sub-carriers are allocatedto each mobile telephone 3 depending on the supported bandwidth of themobile telephone 3 and the amount of data to be sent to the mobiletelephone 3. In this embodiment the base stations 5 also allocate thesub-carriers used to carry the data to the respective mobile telephones3 in order to try to maintain a uniform distribution of the mobiletelephones 3 operating across the base station's bandwidth. When amobile telephone 3 moves from the cell of a source base station (e.g.base station 5-1) to a target base station (e.g. base station 5-2), ahandover (HO) procedure (protocol) is carried out in the source andtarget base stations 5 and in the mobile telephone 3, to control thehandover process.

Base Station

FIG. 7 is a block diagram illustrating the main components of each ofthe base stations 5 used in this embodiment. As shown, each base station5 includes a transceiver circuit 21 which is operable to transmitsignals to and to receive signals from the mobile telephones 3 via oneor more antennae 23 (using the above described sub-carriers) and whichis operable to transmit signals to and to receive signals from thetelephone network 7 via a network interface 25. A controller 27 controlsthe operation of the transceiver circuit 21 in accordance with softwarestored in memory 29. The software includes, among other things, anoperating system 31 and a downlink scheduler 33. The downlink scheduler33 is operable for scheduling user data packets to be transmitted by thetransceiver circuit 21 in its communications with the mobile telephones3. The software also includes a handover module 35, the operation ofwhich will be described below.

Mobile Telephone

FIG. 8 schematically illustrates the mam components of each of themobile telephones 3 shown in FIG. 6. As shown, the mobile telephones 3include a transceiver circuit 71 that is operable to transmit signals toand to receive signals from the base station 5 via one or more antennae73. As shown, the mobile telephone 3 also includes a controller 75 whichcontrols the operation of the mobile telephone 3 and which is connectedto the transceiver circuit 71 and to a loudspeaker 77, a microphone 79,a display 81, and a keypad 83. The controller 75 operates in accordancewith software instructions stored within memory 85. As shown, thesesoftware instructions include, among other things, an operating system87. In this embodiment, the memory also provides uplink data buffers 89.The software for controlling the handover process is provided by ahandover module 91, the operation of which will be described below.

In the above description, both the base station 5 and the mobiletelephones 3 are described for ease of understanding as havingrespective discrete handover modules which control the handoverprocedure when a mobile telephone 3 moves from a source base station toa target base station. Whilst the features may be provided in this wayfor certain applications, for example where an existing system has beenmodified to implement the invention, in other applications, for examplein systems designed with the inventive features in mind from the outset,the handover features may be built into the overall operating system orcode and so a handover module as a discrete entity may not bediscernible.

Description of the Related Handover Protocol

The following description will use the nomenclature used in the LongTerm Evolution (LIE) of UTRAN. Therefore, the mobile telephone 3 that ischanging base stations will be referred to as a UE, the source basestation 5-1 will be referred to as the source eNodeB and the target basestation 5-2 will be referred to as the target eNodeB. The protocolentities used in LTE have the same names as those used in UMTS exceptfor the Radio Link Control (RLC) entities which, under LTE, are calledthe Outer ARQ entities. The Outer ARQ entities of LIE have substantiallythe same (although not identical) functionality to the RLC entities ofUMTS.

FIG. 9 illustrates part of a protocol stack (lower three layers) used inthe UE and eNodeBs. The first layer is the physical layer (L1) which isresponsible for the actual transmission of the data over the radiocommunication channel. Above that is the second layer (L2), which isdivided into two sub-layers—the Medium Access Control layer (L2/MAC)which is responsible for controlling access to the air interface; andthe Outer ARQ layer (L2/OARQ) which is responsible for concatenation andsegmentation of data packets, the acknowledgment of packets and there-transmission of data packets where necessary. Above the second layeris the Radio Resource Control (RRC) layer (L3/RRC) that is responsiblefor controlling radio resources used in the air interface between theeNodeB and the UE. As shown, the L2/Outer ARQ layer includes a number ofOuter ARQ entities 95 used to manage the transmission of C-plane dataand a number of Outer ARQ entities 97 used to manage the transmission ofU-plane data.

FIG. 10 illustrates the related control plane (C-plane) signallingsequence for controlling handover as defined in TR 25.912. As shown, thesequence proceeds as follows

-   1) The UE context within the source eNodeB contains information    regarding roaming restrictions which were provided either at    connection establishment or at the last TA (Tracking Area) update.-   2) The source eNodeB entity configures the UE measurement procedures    according to the area restriction information. Measurements provided    by the source eNodeB entity may assist the function controlling the    UE's connection mobility.-   3) Based on measurement results from the UE and the source eNodeB,    probably assisted by additional Radio Resource Management (RRM)    specific information, the source eNodeB decides to handover the UE    to a cell controlled by the target eNodeB.-   4) The source eNodeB issues a handover Request to the target eNodeB    entity passing necessary information to prepare the handover at the    target side. The target eNodeB configures the required resources.-   5) Admission Control is performed by the target eNodeB to increase    the likelihood of a successful handover, if the resources can be    granted by target eNodeB.-   6) The handover preparation is finished at the target side,    information for the UE to reconfigure the radio path towards the    target side is passed to the source eNodeB.-   7) The UE is commanded by the source eNodeB to perform the handover,    target side radio resource information is contained in the command.-   8) The UE gains synchronization at the target side.-   9) Once the UE has successfully accessed the cell, it sends an    indication to the target eNodeB that the handover is completed.-   10) The Mobility Management Entity (MME)/User Plane Entity (UPE)    (which are two logical entities in the AGW—MME is for C-Plane    Management and UPE is for U-Plane management. It is assumed that    both of them may be in one node, the AGW are informed that the UE    has changed cell. The UPE switches the data path to the target side    and can release any User Plane (U-plane) or Transport Network Layer    (TNL) resources towards the source eNodeB.-   11) The MME/UPE confirms the handover Complete message with the    handover Complete ACK message.-   12) The target eNodeB sends the sources eNodeB a Release Resource    message that triggers the release of resources at the source side.    The target eNodeB can send this message directly after reception of    message 9.-   13) Upon receipt of the Release Resource message, the source eNodeB    can release radio and Control Plane (C-plane) related resources in    relation to the UE context. The source eNodeB should continue to    perform data forwarding to the target eNodeB until an implementation    dependent mechanism decides that data forwarding can be stopped and    U-plane/TNL resources can be released.-   14) If the new cell is a member of a new Tracking Area, the UE needs    to register with the MME/UPE which in turn updates the area    restriction information on the target side.

The description that follows mainly applies to acknowledge mode (AM)Radio Link Control (RLC), in which receipt of data packets areacknowledged by the receiver, although the Outer ARQ entity (theequivalent of RLC for LTE) may not be identical to the RLC in allaspects. Specifics of unacknowledged mode (UM) Outer ARQ entitiesemployed for real time applications such as VoIP and streaming are alsobrought out wherever there is a different handling applied as comparedto the acknowledge mode entities.

In order to transfer the context and forward the data to supportlossless inter eNodeB handover, we have appreciated that it is desirablethat the source eNodeB is able to synchronize the data transmissionstatus between itself and the target eNodeB during handover. From thiswe have concluded that the data flow should desirably be stopped at anappropriate instant in time during the handover execution phaseconsidering that the interruption time for the User Plane data isminimal. However, fulfilling this desired requirement is notstraightforward as stopping the data transmission through additionalsignalling would be problematic as it would increase the overallhandover time. We have appreciated that it is possible implicitly tostop the data transmission in (one or both, preferably both) the sourceeNodeB and UE at the time of handover execution, by modifying therelated approach (which is carried out solely in the C-plane) to buildin some “realization” of the handover process in the User plane datatransfer process. A further desirable feature is that, whether, OuterARQ Service Data Units (SDUs) or Outer ARQ Protocol Data Units (PDUs)based forwarding is adopted, the number of duplicated packetstransmitted over the air either by the target eNodeB or by the UE isminimized.

The inventor has proposed that the signalling sequence in FIG. 10 bemodified as shown in FIG. 11 which shows timings when it is proposed tostop the U-plane data transmission in the Downlink (DL) and the Uplink(UL), together with the details of the modified sequences described. Thefollowing description explains how this approach of stopping the dataflow facilitates achieving a fast lossless handover for LTE.

Referring to FIG. 11, information flow for Intra-LTE-Access MobilitySupport is described.

-   1) The UE context-within the source eNodeB contains information    regarding roaming restrictions which were provided either at    connection establishment or at the last TA update.-   2) The source eNodeB entity configures the UE measurement procedures    according to the area restriction information. Measurements provided    by the source eNodeB entity may assist the function controlling the    UE's connection mobility.-   3) Based on measurement results from the UE and the source eNodeB,    probably assisted by additional RRM specific information, the source    eNodeB decides to handover the UE to a cell controlled by the target    eNodeB.-   4) The source eNodeB issues a handover Request to the target eNodeB    entity passing necessary information to prepare the handover at the    target side. The target eNodeB configures the required resources.-   5) Admission Control is performed by the target eNodeB to increase    the likelihood of a successful handover, if the resources can be    granted by target eNodeB.-   6) The handover preparation is finished at the target eNodeB,    information for the UE to reconfigure the radio path towards the    target eNodeB is passed to the source eNodeB.-   7) This step consists of the following sub steps.

a. Before submitting the HO Command to the lower protocol layers, theRadio Resource Control (RRC) entity 96 in the source eNodeB commands theOuter ARQ User Plane (UP) entities 97 to stop the DL transmission sothat these Outer ARQ entities 97 shall not submit any Outer ARQ PDUs tothe lower protocol layer. The UL reception should continue. In casereceiving packets are UM Outer ARQ PDUs, the Outer ARQ entity willreassemble the SDUs and transfer them to the upper layers as soon as allPDUs that contain the SDU have been received. As regards the AM OuterARQ PDUs, if a Piggybacked ACK/NACK feedback is found in an AMD PDU, itis delivered to the Retransmission buffer & Management Unit at thetransmitting side of the AM Outer ARQ entity, in order to purge thebuffer of positively acknowledged AMD PDUs.

b. The UE is commanded by the source eNodeB RRC entity 96 to perform theHO, target side radio resource information is contained in the command.

c. On receiving the HO Command the RRC entity 96 in the UE commands theouter ARQ U-plane entities to stop the UL transmission. The UE shallimmediately initiate the L1/L2 signalling in the target eNodeB afterthis.

d. Since the user plane data transmission is stopped in both directions,the source eNodeB will be able to accurately synchronize the datatransmission status between source and target eNodeBs, and DL SDUforwarding (from Source eNodeB to target eNodeB) can start from anypoint after this.

-   8) The UE gains synchronization at the target side.-   9) Once the UE has successfully accessed the cell, it sends an    indication to the target eNodeB that the handover is completed.-   10a) After submitting the handover Complete to the lower layer, the    RRC entity 96 in the UE commands the Outer ARQ U-plane entities 97    to resume the UL U-plane traffic.-   10b) On reception of handover Complete, the RRC entity 96 in the    target eNodeB commands the Outer ARQ U-plane entities 97 to resume    the DL traffic. The target eNodeB starts the transmission of the    forwarded DL packets received from the source eNodeB.-   11) The MME/UPE is informed that the UE has changed cell. The UPE    switches the data path to the target eNodeB and can release any    U-plane/TNL resources towards the source eNodeB.-   12) The MME/UPE confirms the handover Complete message to the target    eNodeB with the handover Complete ACK message.-   13) The target eNodeB triggers the release of resources at the    source side. The target eNodeB can send this message directly after    reception of message 9.-   14) Upon reception of the Release Resource message, the source    eNodeB releases radio and C-plane related resources in relation to    the UE context. The source eNodeB continues to perform data    forwarding until an implementation dependent mechanism decides that    data forwarding can be stopped and U-plane/TNL resources can be    released.-   15) If the new cell is a member of a new Tracking Area, the UE needs    to register with the MME/UPE which in turn updates the area    restriction information on the target eNodeB.

The precise timings that are indicated above for stopping the data flowhelp in meeting the following (separate) desiderata we have formulated.

I. Unified Lossless handover mechanism for both real-time and nonreal-time services.

II. Minimal interruption time for the user plane data.

III. Minimizing transmission of duplicate packets by eNodeB and UE.

Desideratum I is met by having Outer ARQ entities 97 which are capableof buffering and forwarding the DL data packets form source to targeteNodeB. In the UE the Outer ARQ entities 97 may buffer the data packetsgenerated by the application after the UL transmission is stopped untilthe UE is switched to the target eNodeB—this requires the UE to providebuffering not present in a conventional UE, but this may not be undulyproblematic to implement. By implicitly stopping the data flows thesource eNodeB can synchronize the data transmission status betweensource and target eNodeB. This is because the source eNodeB can knowaccurately which are the DL SDUs that need to be transferred to thetarget eNodeB based on the data in the transmission and retransmissionbuffer of the AM Radio Bearer (RB) and in the Transmission buffer of UMRB as this remains static after the data flow is stopped.

Regarding the desideratum II, since there is no explicit (additional)signaling involved for stopping the data flow in the UL as well as theDL directions, there will be no increase in the interruption time forthe user plane data.

Furthermore, the instance when the DL data is stopped is chosen to bemost optimal according to our considerations so as to have minimuminterruption time. If the source eNodeB continues to schedule DL data,the UE will not be able to successfully receive or acknowledge thesedata packets as, immediately after receiving the handover command, itwould try to synchronize with the target cell. Eventually these packetswould have to be forwarded to the target eNodeB and will have to betransmitted again through the target eNodeB resulting in inefficientusage of the air interface bandwidth. Whilst according to conventionalthinking it might be argued that for real-time services such as VoIP,stopping the data would be detrimental to the service, we haveappreciated that if the source eNodeB continues to transmit DL packetsthere is no mechanism by which they could be recovered if the UE couldnot receive them while it is trying to synchronize with the target celland this might, in practice, be at least as problematic. However we haveappreciated that if data flow is stopped and a packet forwardingmechanism is adopted, there is a possibility to eliminate packet loss inthe DL, although there could be a delayed data packet delivery to the UEwhich could result in just a single packet being discarded in the worstcase. But this could be compensated through the play-out buffer.

Similarly if the UE continues to transmit in the UL while trying to gainsynchronization with the target cell, it may not be able to receiveacknowledgements from the source eNodeB and the UE would have to againtransmit these AM packets in the UL direction to the target eNodeBresulting in inefficient usage of the air interface bandwidth. For realtime (RT) services, packets that are transmitted in the UL direction bythe UE while it is trying to gain synchronization in the target eNodeB,may get lost due to bad radio conditions in the UL and could not berecovered if the data flow is not stopped. Hence it would be beneficialto avoid any packet loss even for real time services in the UL bystopping the UL data flow during handover execution while the delaycould be compensated at the receiving end by the play out buffer.

Furthermore if the transmission of data continues both in the UL and DLdirections after the handover Command is sent by the source eNodeB, itwould be complicated to synchronize the data transmission status betweensource and target eNodeBs because of the dynamic nature of the packetsin the transmission and retransmission buffers at the source eNodeB andwould result in duplicated packets being transmitted again by the targeteNodeB in the DL and by the UE in the UL to ensure lossless handover fornon-real time (NRT) Services resulting in inefficient usage of the airinterface bandwidth. However, for real-time services such as VoIP etcusing UM mode, data packets transmitted by the source eNodeB and notreceived correctly at the target eNodeB, will be lost and cannot berecovered. Hence stopping the data flow for both RT and NRT services ina unified way will help in better resource utilization on the airinterface for the NRT Bearers and will avoid data loss for RT services.

Another advantage of having a definitive time instant for stopping thedata flow is that a simplified implicit reordering of the data packetsin the target eNodeB can be achieved if the forwarded DL data packetsfrom the source eNodeB on the X2 interface are transmitted first to theUE followed by the data received from the Access Gateway (AGW) on the S1interface.

From the above discussion it seems desirable to stop the UL and DL datatransmission during the handover execution for both RT and NRT Servicesto support lossless Inter eNodeB handover, while aiming to keep theinterruption time and transmission of duplicate packets to a minimum.

Outer ARQ Requirements

In order to support the above lossless/seamless handover the outer ARQentities should have the following requirements.

SDU Level Buffer Management

The re-establishment of a new link layer (L2) connection with the targeteNodeB during inter eNodeB handover causes the Outer ARQ entities of thesource eNodeB as well as the UE to flush out the Outer ARQ PDUs from theoutstanding transmit and re-transmit buffers. The flushing ofoutstanding radio frames produces noticeable impact on the performanceof the end-to-end application.

In this embodiment, in order to minimize or eliminate packet loss duringintra-LTE inter eNodeB handover, the outer ARQ entity 97 maintains a newSDU buffer management entity for both AM and UM mode data packets. FIG.12 illustrates this new SDU buffer management entity 101 for AM modedata packets and FIG. 13 illustrates this new SDU buffer managemententity 103 for UM mode data packets. As shown in FIG. 12, the SDU buffermanagement entity 101 buffers (stores a copy of) each incoming AM SDUbefore sending it to the concatenation and segmentation entity 105within the outer ARQ layer. The segmented packets (PDUs) are then outputto a multiplexer 107 and at the same time copied into a PDUretransmission buffer and management entity 109. A PDU received from theconcatenation and segmentation entity 105 or a PDU requiringre-transmission is then passed through the multiplexer 107 to thetransmission buffer 111 for submission to the lower layer (L2/MAC).Acknowledgements received back from the receiving terminal are receivedby the PDU retransmission buffer and management entity 109 and used tocontrol the retransmission of PDUs that are not acknowledged. Once thePDU retransmission buffer and management entity 109 can infer that allthe segments belonging to a SDU have been successfully delivered to theARQ layer of the peer device, it provides a feedback trigger(identifying that SDU) to the SDU buffer management entity 101, througha new interface 113. For example, the PDU Retransmission and Buffermanagement entity 109 in the eNodeB will send this feedback trigger whenit is able to decide that all the segments belonging to a SDU have beensuccessfully received by the ARQ layer in the receiving UE. Uponreceiving this feedback trigger, the SDU buffer management entity 101uses the information contained in the feedback trigger to flush (remove)the corresponding SDU stored in its buffer.

Similarly, as illustrated in FIG. 13, incoming UM mode data packets arecopied and buffered by the SDU Buffer Management entity 103 and thenpassed onto the concatenation and segmentation entity 105 forconcatenation and segmentation into PDUs. The PDUs are then output tothe transmission buffer 111 for submission to the lower layer (L2/MAC).Once all the PDUs belonging to a SDU have been submitted to the MAC fortransmission, the transmission buffer 111 sends a feedback trigger (overa new interface 115) identifying that SDU to the SDU buffer managemententity 103. In response, the SDU buffer management entity 103 flushesthat SDU from its buffer.

When stopping the ARQ entity during HO, the PDU retransmission andbuffer management entity 109 for AM data and the transmission bufferentity 111 for UM data would also send the feedback to the SDU buffermanagement entity 101/103 if an SDU was transmitted just before the DLtransmission is stopped. In this way, the SDU buffer management entity101/103 can update its SDU buffers so that they contain only those SDUsthat have not yet been transmitted in full to the UE.

On the network side, the SDU buffer management entity 101/103 in thesource eNodeB forwards only the undelivered DL SDUs (which are stored inthe SDU buffer management entity 101/103) to the target eNodeB to ensurezero downlink packet loss and minimizing transmission of duplicatepackets. The SDU buffer management entity 101/103 in the source eNodeBstarts to forward the buffered packets to the target eNodeB (through thetunnel established over the X215 interface), when it receives a commandto do so from the RRC layer (L3).

At the UE, the SDU buffer management entity 101/103 will send thebuffered packets on resumption of data flow in the UL after HO iscompleted (i.e. after sending the HO Complete message), to the targeteNodeB to ensure zero uplink packet loss and to minimize transmission ofduplicate packets.

Unidirectional Stopping of the Outer ARQ Entities

Since data transmission is being stopped in the source eNodeB and in theUE at the time of handover execution, it needs to be emphasized thatsuspending the user plane data transfer in both directions (as in aconventional REL 6 RLC entity) would result in data loss as the datapackets in flight will be discarded by the RLC entity that has beenstopped. Hence for a LTE system where there will be hard handovers, theouter ARQ entity (RLC) should stop transmissions but continue to receivepackets to avoid any data loss.

Before submitting the HO Command to the lower layers, the RRC entity 96in the source eNodeB commands the Outer ARQ U-plane entities to stop theDL transmission. The UL reception should continue. In case receivingPDUs are UM Outer ARQ PDUs, the Outer ARQ entity will reassemble SDUsand transfer them to the upper layers as soon as all PDUs that containthe SDU have been received. As regards the AM Outer ARQ PDUs, if aPiggybacked ACK/NACK feedback is found in an AMD PDU, it is delivered tothe Retransmission buffer & Management entity 109 at the transmittingside of the AM Outer ARQ entity, in order to purge the buffer ofpositively acknowledged AMD PDUs. Similarly on receiving the HO Commandthe RRC entity 96 in the UE commands the Outer ARQ U-plane entities tostop the UL transmission. This functionality therefore requires aprimitive (command) from the RRC entity 96 which will indicate thedirection in which the data flow needs to be stopped.

Sending STAUS PDU Before Stopping of the Outer ARQ Entities

In order to transfer the context and forward the data to supportlossless inter eNodeB HO, the source eNodeB synchronizes the datatransmission status between itself and the target data eNodeB during HO.This is facilitated by stopping the data flow at an appropriate instantin time during the HO execution phase, considering that the interruptiontime for the user plane data is minimal. In one embodiment the Outer ARQentity in the source eNodeB and in the UE sends the other a statusreport (indicating what that device has received successfully) beforestopping the data flow in the appropriate direction. This status messagemay be a simplified report indicating only what the device has received.This allows the source eNodeB and the UE to get know the exact datatransmission status (i.e. what the other party has received andtherefore what still has to be sent) before stopping the transmissionduring the HO execution. Therefore, after the HO the data transmissioncan resume without the need to transmit any duplicated packets over theair interface.

This functionality requires a primitive (command) from the RRC entity 96which instructs the outer ARQ entities 97 to send a Status PDU beforestopping the data transmission.

Glossary of 3GPP Terms

-   LTE—Long Term Evolution (of UTRAN)-   eNodeB—E-UTRAN Node B-   AGW—Access Gateway-   UE—User Equipment—mobile communication device-   DL—downlink—link from base to mobile-   UL—uplink—link from mobile to base-   AM—Acknowledge Mode-   UM—Unacknowledge Mode-   MME—Mobility Management Entity-   UPE—User Plane Entity-   HO—Handover-   RLC—Radio Link Control-   RRC—Radio Resource Control-   RRM—Radio Resource Management-   SDU—Service Data Unit-   PDU—Protocol Data Unit-   TA—Tracking Area-   U-plane—User Plane-   TNL—Transport Network Layer-   S1 Interface—Interface between Access Gateway and eNodeB-   X2 Interface—Interface between two eNodeB

The following is a detailed description of the way in which the presentinventions may be implemented in the currently proposed 3GPP LIEstandard. Whilst various features are described as being essential ornecessary, this may only be the case for the proposed 3GPP LIE standard,for example due to other requirements imposed by the standard. Thesestatements should not, therefore, be construed as limiting the presentinvention in any way.

1. Introduction

The signalling flow for the control plane signalling with coordinationbetween the RRC signaling and pausing/resuming of the U-plane data toachieve Lossless/Seamless Intra-LTE Handover is discussed in [1]. Toachieve the lossless/seamless handovers there are certain requirementsthat need to be fulfilled by the outer ARQ entities.

In this contribution we discuss these Outer ARQ requirements to supportLossless/Seamless HO for Intra LTE Handover.

2. Discussion

In order to support lossless/seamless handover following requirementsneeds to be supported by the outer ARQ entities.

2.1 SDU Level Buffer Management

The re-establishment of a new link layer connection with target eNBduring inter eNB handover causes the outer ARQ layers of source eNB aswell as the UE to flush out the RLC PDUs from the outstanding transmitand re-transmit buffers. The flushing of outstanding radio framesproduces noticeable impact on the performance of end-to-end application.

In order to minimize or eliminate packet loss during intra-LTE inter eNBhandover, it is necessary that the outer ARQ entity maintains a new SDUbuffer management entity for both the AM and UM mode as shown in FIG. 6.The SDU buffer management entity buffers the incoming PDCP packet beforesending that to segmentation entity within the outer ARQ layer.

The feedback form the PDU Retransmission and Buffer management entity tothe SDU buffer management entity in the AM mode, through the newinterface 113 in FIG. 12, will be sent once it can infer that all thesegments belonging to a SDU has been successfully delivered to the ARQlayer of the peer device. For example, eNB PDU Retransmission and Buffermanagement entity will send this trigger when it is able to decide thatall the segments belonging to a SDU has been successfully received bythe UE ARQ layer. SDU buffer management entity uses this information toflush the SDU stored in its buffer when indicated by the PDURetransmission and Buffer management entity trigger.

Similarly, for UM mode outer ARQ entity, Transmission Buffer entitywould send a feedback, through the new interface 115 shown in FIG. 13,to SDU buffer management entity once all the PDUs belonging to a SDU hasbeen submitted to the MAC for transmission. SDU buffer management entityshall flush the buffer accordingly.

When stopping the ARO entity during HO, the PDU Retransmission andBuffer management entity for AM and Transmission Buffer entity for UMwould also send the feedback to the SDU buffer management entity so thatit could update its SDU buffers.

On the network side, SDU buffer management entity shall forward only theundelivered DL SDU form the source eNB to target eNB to ensure zerodownlink packet loss and minimizing transmission of duplicate packets. Anew primitive form RRC layer needs to be defined to indicate to the SDUbuffer management entity to start forwarding the buffered packet fromsource eNB to the target eNB through the tunnel established over the X2interface.

At the UE, the SDU buffer management entity will send the bufferedpacket on resumption of data flow in the UL after HO is completed (i. e.after sending HO Complete), through the target eNB to ensure zero uplinkpacket loss and minimizing transmission of duplicate packets

2.2 Unidirectional Stopping of the Outer ARQ Entities

Since we need to stop the data transmission in the source eNB and UE atthe time of handover execution, it needs to be emphasized thatsuspending the user plane data transfer in both direction as inconventional REL 6 RLC entity would result in data loss as the datapackets in flight will be discarded by the RLC entity that has beenstopped. Hence for a LTE system where there will be hard handovers, itis necessary that the Outer ARQ entity stops transmissions but continueto receive the packets to avoid any data loss.

Before submitting HO Command to the lower layers, the RRC entity in eNBwould command the Outer ARQ ENTITY UP entities to stop the DLtransmission. The UL reception could continue. In case receivingentities are UM Outer ARQ ENTITY entities, it will reassemble SDUs andtransfer them to the upper layers as soon as all PDUs that contain theSDU have been received. As regards the AM Outer ARQ ENTITY entities, ifa Piggybacked ACK/NACK feedback is found in an AMD PDU, it is deliveredto the Retransmission buffer & Management Unit at the transmitting sideof the AM Outer ARQ ENTITY entity, in order to purge the buffer ofpositively acknowledged AMD PDUs. Similarly on receiving the HO Commandthe RRC entity in the UE would command the Outer ARQ ENTITY UP entitiesto stop the UL transmission.

This functionality would therefore require a primitive from RRC whichwill indicate the direction in which the data flow needs to be stopped.

2.2 Sending STAUS PDU Before Stopping of the Outer ARQ Entities

In order to transfer the context and forward the data to supportlossless inter eNB HO, it is necessary that the source eNB is able tosynchronize the data transmission status between itself and target dataeNB during HO. This would in turn require that the data flow should bestopped at appropriate instant in time during HO execution phaseconsidering that the interruption time for the user plane data isminimal. If the Outer ARQ entity sends a status report before stoppingthe data flow in a particular direction, it would facilitate the sourceeNB and the UE to get know the exact data transmission status beforestopping the transmission during HO execution. After the HO the datatransmission can resume without the need to transmit any duplicatedpackets over the air interface.

This functionality would require a primitive which would indicate theouter ARQ entities to send a Status PDU before stopping a data.

3. Conclusion

In this paper, we discuss in detail the outer ARQ functionality neededfor supporting the lossless/seamless inter eNB handover while aiming tokeep transmission of duplicate packet to a minimum. It is proposed tocapture the Outer ARQ functionality requirement from the discussion andinclude it in the Stage 2 TS form this paper.

4. Reference

[1] R2-060XXX Intra LTE Lossless/Seamless Handover

[2] R2-062725, E-UTRAN Stage 2 v004

The invention claimed is:
 1. A target eNB comprising: a receiverconfigured to receive data from an S1 interface and to receive data froman X2 interface, wherein the S1 interface is an interface between thetarget eNB and a gateway and the X2 interface is an interface between asource eNB and the target eNB; and a transmitter configured to send, fora radio link control acknowledge mode bearer, to a user equipment(‘UE’), after receiving a handover complete message from the UE,downlink data received from the X2 interface before sending, to the UE,downlink data received from the S1 interface with the exception of datafor which reception was acknowledged by the UE.
 2. A communicationcontrol method executed by a target eNB, the communication controlmethod comprising: receiving data from an S1 interface and receivingdata from an X2 interface, wherein the S1 interface is an interfacebetween the target eNB and a gateway and the X2 interface is aninterface between a source eNB and the target eNB; and sending, for aradio link control acknowledge mode bearer, to a user equipment (‘UE’),after receiving a handover complete message from the UE, downlink datareceived from the X2 interface before sending, to the UE, downlink datareceived from the S1 interface with the exception of data for whichreception was acknowledged by the UE.